-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transaction validity and to-plain conversion for PoW transactions #3187
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sisou
force-pushed
the
nibhar/tx-history
branch
from
December 10, 2024 20:51
fffc91b
to
82bd171
Compare
jsdanielh
reviewed
Dec 12, 2024
sisou
force-pushed
the
nibhar/tx-history
branch
from
December 12, 2024 13:25
602b7f3
to
0e54f87
Compare
sisou
changed the title
WIP: Transaction validity and to-plain conversion for PoW transactions
Transaction validity and to-plain conversion for PoW transactions
Dec 12, 2024
Ready for review. |
jsdanielh
reviewed
Dec 12, 2024
3 tasks
sisou
force-pushed
the
nibhar/tx-history
branch
from
December 13, 2024 10:34
0e54f87
to
4c93e43
Compare
jsdanielh
approved these changes
Dec 13, 2024
PoW contract creation data was different than in PoS, leading to failing deserializations when converting a transaction to its plain format in the web-client.
Added special handling for PoW network IDs and added tests for basic txs, vesting and HTLC creation txs and HTLC claiming txs.
Where it makes sense.
The problem was the merkle path, whose serialization changed in PoS.
Also - refactor `genesis_number` => `genesis_block_number` - clean up example page changes
jsdanielh
force-pushed
the
nibhar/tx-history
branch
from
December 13, 2024 21:29
4c93e43
to
a9c1ac4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ensure PoW transactions can be properly converted to their plain representation, which is primarily done during address transaction history fetching in the web-client. Before this change, PoW transactions could not be returned and the process panicked, due to different serializations of contract creation data, HTLC proofs and signature proofs.
I have tried to document all changes and differences in code comments, let me know if you require more info, here or in the code.
Pull request checklist
clippy
andrustfmt
warnings.